Implement LeaderElectionRunnable interface for CertRotator #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This MR implements
LeaderElectionRunnable
forCertRotator
. This is needed for case when theCertRotator
is used in manager that implements leader election. In such case we might want to runCertRotator
in all replicas (now this will be default) instead of running only on the leader (currently the default). The reason why we need to runCertRotator
on all replicas is to unblock the registering the webhooks (which wait for theCertRotator
to finish setup) on all replicas (webhooks by default run on all replicas even in leader election mode).This change has no impact on workflows that don't use leader election like gatekeeper.
See kubernetes-sigs/controller-runtime#424 and kubernetes-sigs/controller-runtime#441 for more context.